bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 19 Mar 2020 08:50:20 +0000 (08:50 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Thu, 19 Mar 2020 08:50:20 +0000 (08:50 +0000)
commit1a11ddc2a00624c17ee83d3b32281d0bfe9f8faa
tree5a231eb661c23095a2027dce78c74a98beee4bfa
parent449ee985a9c1bb4a6d2c2afdb851a7ce06438f08
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h